Release 10.1A: OpenEdge Data Management:
SQL Development

OpenEdge SQL and Progress 4GL security

To properly maintain security of your OpenEdge database, it is important to understand how OpenEdge SQL and Progress 4GL work together in controlling database access.

Progress 4GL security

A Progress 4GL database is an open system. OpenEdge applies no security restrictions on a newly created 4GL database. Users are able to access the database without being prompted for a valid user name or password. When no users are created, the 4GL will not display a log-in dialog box. However, the Progress 4GL database administrator can use the Data Administration tool to establish security by creating users and granting privileges.

For information on using the Data Administration tool, see OpenEdge Data Management: Database Administration .

OpenEdge SQL security

SQL is a closed system and always requires a user identification and password to gain database access. However, an SQL database is not secure until users are created and assigned passwords. An SQL database with no assigned users will simply grant access for any identification or password provided. Once the DBA creates the first user, the SQL database will only grant access to users who provide valid names and passwords.

How 4GL and SQL control security together

OpenEdge provides a user table that is shared between the SQL and 4GL environments. In so doing, users can use either Progress 4GL or SQL to manipulate an OpenEdge database. For instance, creating a first user via SQL is equivalent to creating a user from the OpenEdge Data Administration tool. The user list maintained via SQL is updated for the 4GL as well.

Note: The 4GL security model is enforced for 4GL clients and servers only. Similarly, the SQL security model is enforced only for SQL clients and servers.